| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CP.6.1.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.6.1 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CP_6_1_Manage_Medication_Administration |
| Title | CP.6.1 Manage Medication Administration (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Present providers with the list of medications that are to be administered to a patient, necessary administration information, and capture administration details. |
| Purpose | In a setting in which medication orders are to be administered by a provider rather than the patient, the necessary information is presented including: the list of medication orders that are to be administered; administration instructions, times or other conditions of administration; dose and route, etc. The system shall securely relate medications to be administered to the unique identity of the patient (see [[CPS.1.1]]). Additionally, the provider can record what actually was or was not administered, whether or not these facts conform to the order. Appropriate time stamps for all medication related activity are generated. For some settings that administer complete sets of medications from a variety of providers' orders, it may be useful to provide an additional check for possible drug-drug or other interactions. The EHR system shall support the five “rights” - Right Patient, Right Drug, Right Dose, Right Route, Right Time. The system should report medication administration, where appropriate, to public health or disease management authorities (e.g., oncology related medication orders should be communicated or transmitted to a cancer registry). |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Present providers with the list of medications that are to be administered to a patient, necessary administration information, and capture administration details.
In a setting in which medication orders are to be administered by a provider rather than the patient, the necessary information is presented including: the list of medication orders that are to be administered; administration instructions, times or other conditions of administration; dose and route, etc. The system shall securely relate medications to be administered to the unique identity of the patient (see [[CPS.1.1]]). Additionally, the provider can record what actually was or was not administered, whether or not these facts conform to the order. Appropriate time stamps for all medication related activity are generated.
For some settings that administer complete sets of medications from a variety of providers' orders, it may be useful to provide an additional check for possible drug-drug or other interactions.
The EHR system shall support the five “rights” - Right Patient, Right Drug, Right Dose, Right Route, Right Time.
The system should report medication administration, where appropriate, to public health or disease management authorities (e.g., oncology related medication orders should be communicated or transmitted to a cancer registry).
| CP.6.1#01 | SHALL |
The system SHALL provide the ability to render the list of medications that are to be administered. |
| CP.6.1#02 | SHALL |
The system SHALL provide the ability to render the list of medications that are to be administered including all administration directions/instructions (SIG). |
| CP.6.1#03 | SHOULD |
The system SHOULD provide the ability to render medications as dispensed (including dose and quantity of dispensed units of medication). |
| CP.6.1#04 | SHOULD |
The system SHOULD provide the ability to tag the medications that are to be administered by the patient (i.e. self-administered). |
| CP.6.1#05 | SHALL |
The system SHALL provide the ability to render the drug, dose, route, time and frequency of desired administration for all scheduled medications. |
| CP.6.1#06 | SHOULD |
The system SHOULD provide the ability to render a notification to the clinician when specific doses are due. |
| CP.6.1#07 | SHOULD |
The system SHOULD provide the ability to render a notification when medication related activities are due (e.g., adjusting medication dosing based on patient condition, checking IV lines for infiltration). |
| CP.6.1#08 | SHALL |
The system SHALL conform to function [[CPS.4.2.1]] (Support for Medication Interaction and Allergy Checking) in order to determine and render allergies, drug-drug interactions, and other potential adverse reactions, when rendering medication administration information. |
| CP.6.1#09 | SHALL |
The system SHALL conform to function [[CPS.4.2.2]] (Support for Patient-Specific Dosing and Warnings) in order to determine and render other potential adverse reactions, when rendering medication administration information. |
| CP.6.1#10 | SHALL |
The system SHALL provide the ability to capture and maintain the medication identification number of the drug administered to the patient (e.g., NDC number, lot numbers, expiration date). |
| CP.6.1#11 | dependent SHALL |
The system SHALL provide the ability to capture, maintain, and render medication administration details as discrete data, including:
|
| CP.6.1#12 | SHOULD |
The system SHOULD provide the ability to capture the effectiveness of PRN or "as needed" doses after they have been administered. |
| CP.6.1#13 | SHOULD |
The system SHOULD provide the ability to render any clinical interventions or assessments required prior to medication administration. |
| CP.6.1#14 | SHOULD |
The system SHOULD provide the ability to render any clinical interventions or assessments required subsequent to medication administration. |
| CP.6.1#15 | SHOULD |
The system SHOULD provide the ability to link securely medication-related activities to the unique identity of the patient (e.g., linking the verification of medication administration to the correct patient). |
| CP.6.1#16 | SHOULD |
The system SHOULD provide the ability to capture the identification of medication samples dispensed, including lot number and expiration date. |
| CP.6.1#17 | SHOULD |
The system SHOULD provide the ability to capture, maintain, and render patient identification and medication identification information from integrated point-of-care devices (e.g., barcode recognition devices that help verify patients and their medications). |
| CP.6.1#18 | SHOULD |
The system SHOULD provide the ability to render medication orders for medications that have not yet been dispensed. |
| CP.6.1#19 | SHOULD |
The system SHOULD provide the ability to render medication orders for medications that have not yet been administered. |
| CP.6.1#20 | SHOULD |
The system SHOULD render an alert, when rendering medication administration information, if a maximum individual or daily dose exists and further administration would cause these doses to be exceeded (e.g., in the case of a PRN order with weight-based or BSA-based dose limits). |
| CP.6.1#21 | SHOULD |
The system SHOULD provide the ability to render medications to be administered over a selectable date/time range. |
| CP.6.1#22 | SHALL |
The system SHALL provide the ability to render the medication administration history including administering provider, date, and time. |
| CP.6.1#23 | SHOULD |
The system SHOULD provide the ability to render continuous infusions in a manner that distinguishes them from other discrete-dose medications (e.g., insulin drip versus subcutaneous insulin dose). |
| CP.6.1#24 | SHOULD |
The system SHOULD provide the ability to render PRN ("as needed") medications in a manner that distinguishes them from other medications. |
| CP.6.1#25 | SHOULD |
The system SHOULD provide the ability to annotate a scheduled medication dose and include the annotation as part of the legal medical record (e.g., describing the dose to be administered based upon specific clinical indicators such as a sliding scale insulin order where the dose is based upon the patient's current blood sugar level). |
| CP.6.1#26 | SHALL |
The system SHALL provide the ability to render the medication order as written (i.e., exact clinician order language) when rendering administration information. |
| CP.6.1#27 | SHALL |
The system SHALL provide the ability to capture and render patient-specific instructions or other free text related to the administration of the medication (e.g., use left-arm IV only) |
| CP.6.1#28 | SHALL |
The system SHALL provide the ability to manage information regarding a second provider witness to co-document administration. |
| CP.6.1#29 | SHOULD |
The system SHOULD provide the ability to capture the documentation of medication administration using a barcode scanner or imaging scanner (e.g., scanner capable of reading two dimensional symbologies). |
| CP.6.1#30 | SHOULD |
The system SHOULD provide the ability to render an alert to the administering provider when an electronic identification device (e.g., barcode & scanner or RFID) is used to document the administration of the medication and one of the following is in error: right patient, right medication, right dose, right time, or right route or there has not been positive identification of the administering provider. |
| CP.6.1#31 | SHOULD |
The system SHOULD provide the ability to manage medication administration schedules on the record of medication administration - to allow user to adjust future authorized schedule as needed (e.g., delay, refused, unavailable). |
| CP.6.1#32 | SHOULD |
The system SHOULD provide the ability to render a notification to associated systems (e.g., pharmacy, ordering, food and nutrition services) of changes in schedules on the record of medication administration. |
| CP.6.1#33 | SHOULD |
The system SHOULD provide the ability to capture an acknowledgement from a user that a medication order has been reviewed including capturing the date, time and user credentials. |
| CP.6.1#34 | SHOULD |
The system SHOULD provide the ability to capture documentation of medication administration prior to pharmacy review. |
| CP.6.1#35 | SHALL |
The system SHALL provide the ability to capture, maintain and render as part of the medication administration record for infusions the actual date and times of the infusion including the start and stop times and any modifications to the infusion and the assessment status of the infusion. |
| CP.6.1#36 | SHOULD |
The system SHOULD provide the ability to capture, maintain, and render the patient's consent to have restricted medications administered, (e.g., Risk Evaluation and Mitigation Strategy (REMS)). |
| CP.6.1#37 | dependent MAY |
The system MAY auto-populate the medication administration record as a by-product of verification of administering provider, patient, medication, dose, route and time according to scope of practice, organizational policy, and/or jurisdictional law. |
| CP.6.1#38 | SHOULD |
The system SHOULD provide the ability to capture, maintain, and present physiological parameters or task completion that must be checked and recorded prior to medication administration. |
| CP.6.1#39 | SHOULD |
The system SHOULD provide the ability to capture and maintain documentation that the right patient, right medication, right dose, right time, and right route were verified (e.g., using positive ID technology such as bar code scanning) at the time of administration. |
| CP.6.1#40 | dependent MAY |
The system MAY provide the ability to render a medication unique identifier (e.g., NDC, Structured Products Label (SPL) in the U.S. Realm or other standard product identifiers) according to jurisdictional law. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CP.6.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Present providers with the list of medications that are to be administered to a patient, necessary administration information, and capture administration details.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>In a setting in which medication orders are to be administered by a provider rather than the patient, the necessary information is presented including: the list of medication orders that are to be administered; administration instructions, times or other conditions of administration; dose and route, etc. The system shall securely relate medications to be administered to the unique identity of the patient (see [[CPS.1.1]]). Additionally, the provider can record what actually was or was not administered, whether or not these facts conform to the order. Appropriate time stamps for all medication related activity are generated.</p>\n<p>For some settings that administer complete sets of medications from a variety of providers' orders, it may be useful to provide an additional check for possible drug-drug or other interactions.</p>\n<p>The EHR system shall support the five “rights†- Right Patient, Right Drug, Right Dose, Right Route, Right Time.</p>\n<p>The system should report medication administration, where appropriate, to public health or disease management authorities (e.g., oncology related medication orders should be communicated or transmitted to a cancer registry).</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render the list of medications that are to be administered.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render the list of medications that are to be administered including all administration directions/instructions (SIG).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render medications as dispensed (including dose and quantity of dispensed units of medication).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to tag the medications that are to be administered by the patient (i.e. self-administered).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render the drug, dose, route, time and frequency of desired administration for all scheduled medications.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a notification to the clinician when specific doses are due.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a notification when medication related activities are due (e.g., adjusting medication dosing based on patient condition, checking IV lines for infiltration).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to function [[CPS.4.2.1]] (Support for Medication Interaction and Allergy Checking) in order to determine and render allergies, drug-drug interactions, and other potential adverse reactions, when rendering medication administration information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to function [[CPS.4.2.2]] (Support for Patient-Specific Dosing and Warnings) in order to determine and render other potential adverse reactions, when rendering medication administration information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture and maintain the medication identification number of the drug administered to the patient (e.g., NDC number, lot numbers, expiration date).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture, maintain, and render medication administration details as discrete data, including:</p>\n<ul>\n<li>the medication name, strength and dose;</li>\n<li>date and time of administration;</li>\n<li>route and site;</li>\n<li>administering provider;</li>\n<li>observations, reactions and complications;</li>\n<li>reason medication not given and/or medication related activity not performed;\naccording to scope of practice, organizational policy, and/or jurisdictional law.</li>\n</ul>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture the effectiveness of PRN or "as needed" doses after they have been administered.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#13</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render any clinical interventions or assessments required prior to medication administration.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#14</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render any clinical interventions or assessments required subsequent to medication administration.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#15</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to link securely medication-related activities to the unique identity of the patient (e.g., linking the verification of medication administration to the correct patient).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#16</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture the identification of medication samples dispensed, including lot number and expiration date.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#17</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain, and render patient identification and medication identification information from integrated point-of-care devices (e.g., barcode recognition devices that help verify patients and their medications).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#18</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render medication orders for medications that have not yet been dispensed.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#19</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render medication orders for medications that have not yet been administered.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#20</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD render an alert, when rendering medication administration information, if a maximum individual or daily dose exists and further administration would cause these doses to be exceeded (e.g., in the case of a PRN order with weight-based or BSA-based dose limits).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#21</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render medications to be administered over a selectable date/time range.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#22</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render the medication administration history including administering provider, date, and time.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#23</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render continuous infusions in a manner that distinguishes them from other discrete-dose medications (e.g., insulin drip versus subcutaneous insulin dose).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#24</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render PRN ("as needed") medications in a manner that distinguishes them from other medications.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#25</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to annotate a scheduled medication dose and include the annotation as part of the legal medical record (e.g., describing the dose to be administered based upon specific clinical indicators such as a sliding scale insulin order where the dose is based upon the patient's current blood sugar level).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#26</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render the medication order as written (i.e., exact clinician order language) when rendering administration information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#27</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture and render patient-specific instructions or other free text related to the administration of the medication (e.g., use left-arm IV only)</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#28</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage information regarding a second provider witness to co-document administration.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#29</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture the documentation of medication administration using a barcode scanner or imaging scanner (e.g., scanner capable of reading two dimensional symbologies).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#30</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render an alert to the administering provider when an electronic identification device (e.g., barcode & scanner or RFID) is used to document the administration of the medication and one of the following is in error: right patient, right medication, right dose, right time, or right route or there has not been positive identification of the administering provider.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#31</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage medication administration schedules on the record of medication administration - to allow user to adjust future authorized schedule as needed (e.g., delay, refused, unavailable).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#32</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a notification to associated systems (e.g., pharmacy, ordering, food and nutrition services) of changes in schedules on the record of medication administration.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#33</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture an acknowledgement from a user that a medication order has been reviewed including capturing the date, time and user credentials.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#34</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture documentation of medication administration prior to pharmacy review.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#35</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture, maintain and render as part of the medication administration record for infusions the actual date and times of the infusion including the start and stop times and any modifications to the infusion and the assessment status of the infusion.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#36</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain, and render the patient's consent to have restricted medications administered, (e.g., Risk Evaluation and Mitigation Strategy (REMS)).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#37</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY auto-populate the medication administration record as a by-product of verification of administering provider, patient, medication, dose, route and time according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#38</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain, and present physiological parameters or task completion that must be checked and recorded prior to medication administration.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#39</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain documentation that the right patient, right medication, right dose, right time, and right route were verified (e.g., using positive ID technology such as bar code scanning) at the time of administration.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.6.1#40</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render a medication unique identifier (e.g., NDC, Structured Products Label (SPL) in the U.S. Realm or other standard product identifiers) according to jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.6.1",
"version" : "2.1.0",
"name" : "CP_6_1_Manage_Medication_Administration",
"title" : "CP.6.1 Manage Medication Administration (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Present providers with the list of medications that are to be administered to a patient, necessary administration information, and capture administration details.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "In a setting in which medication orders are to be administered by a provider rather than the patient, the necessary information is presented including: the list of medication orders that are to be administered; administration instructions, times or other conditions of administration; dose and route, etc. The system shall securely relate medications to be administered to the unique identity of the patient (see [[CPS.1.1]]). Additionally, the provider can record what actually was or was not administered, whether or not these facts conform to the order. Appropriate time stamps for all medication related activity are generated.\n\nFor some settings that administer complete sets of medications from a variety of providers' orders, it may be useful to provide an additional check for possible drug-drug or other interactions.\n\nThe EHR system shall support the five “rights†- Right Patient, Right Drug, Right Dose, Right Route, Right Time.\n\nThe system should report medication administration, where appropriate, to public health or disease management authorities (e.g., oncology related medication orders should be communicated or transmitted to a cancer registry).",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-01",
"label" : "CP.6.1#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render the list of medications that are to be administered.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.8.1#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-02",
"label" : "CP.6.1#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render the list of medications that are to be administered including all administration directions/instructions (SIG).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.8.1#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-03",
"label" : "CP.6.1#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render medications as dispensed (including dose and quantity of dispensed units of medication)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-04",
"label" : "CP.6.1#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to tag the medications that are to be administered by the patient (i.e. self-administered)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-05",
"label" : "CP.6.1#05",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render the drug, dose, route, time and frequency of desired administration for all scheduled medications.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.8.1#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-06",
"label" : "CP.6.1#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a notification to the clinician when specific doses are due.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.8.1#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-07",
"label" : "CP.6.1#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a notification when medication related activities are due (e.g., adjusting medication dosing based on patient condition, checking IV lines for infiltration)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-08",
"label" : "CP.6.1#08",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to function [[CPS.4.2.1]] (Support for Medication Interaction and Allergy Checking) in order to determine and render allergies, drug-drug interactions, and other potential adverse reactions, when rendering medication administration information.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.8.1#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-09",
"label" : "CP.6.1#09",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to function [[CPS.4.2.2]] (Support for Patient-Specific Dosing and Warnings) in order to determine and render other potential adverse reactions, when rendering medication administration information.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.8.1#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-10",
"label" : "CP.6.1#10",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture and maintain the medication identification number of the drug administered to the patient (e.g., NDC number, lot numbers, expiration date)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CP.6.1-11",
"label" : "CP.6.1#11",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture, maintain, and render medication administration details as discrete data, including:\n- the medication name, strength and dose;\n- date and time of administration;\n- route and site;\n- administering provider;\n- observations, reactions and complications;\n- reason medication not given and/or medication related activity not performed; \naccording to scope of practice, organizational policy, and/or jurisdictional law.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.8.1#7"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-12",
"label" : "CP.6.1#12",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture the effectiveness of PRN or \"as needed\" doses after they have been administered."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-13",
"label" : "CP.6.1#13",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render any clinical interventions or assessments required prior to medication administration."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-14",
"label" : "CP.6.1#14",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render any clinical interventions or assessments required subsequent to medication administration."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-15",
"label" : "CP.6.1#15",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to link securely medication-related activities to the unique identity of the patient (e.g., linking the verification of medication administration to the correct patient).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.8.1#8"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-16",
"label" : "CP.6.1#16",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture the identification of medication samples dispensed, including lot number and expiration date."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-17",
"label" : "CP.6.1#17",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture, maintain, and render patient identification and medication identification information from integrated point-of-care devices (e.g., barcode recognition devices that help verify patients and their medications)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-18",
"label" : "CP.6.1#18",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render medication orders for medications that have not yet been dispensed."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-19",
"label" : "CP.6.1#19",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render medication orders for medications that have not yet been administered."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-20",
"label" : "CP.6.1#20",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD render an alert, when rendering medication administration information, if a maximum individual or daily dose exists and further administration would cause these doses to be exceeded (e.g., in the case of a PRN order with weight-based or BSA-based dose limits)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-21",
"label" : "CP.6.1#21",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render medications to be administered over a selectable date/time range."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-22",
"label" : "CP.6.1#22",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render the medication administration history including administering provider, date, and time."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-23",
"label" : "CP.6.1#23",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render continuous infusions in a manner that distinguishes them from other discrete-dose medications (e.g., insulin drip versus subcutaneous insulin dose)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-24",
"label" : "CP.6.1#24",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render PRN (\"as needed\") medications in a manner that distinguishes them from other medications."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-25",
"label" : "CP.6.1#25",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to annotate a scheduled medication dose and include the annotation as part of the legal medical record (e.g., describing the dose to be administered based upon specific clinical indicators such as a sliding scale insulin order where the dose is based upon the patient's current blood sugar level)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-26",
"label" : "CP.6.1#26",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render the medication order as written (i.e., exact clinician order language) when rendering administration information."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-27",
"label" : "CP.6.1#27",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture and render patient-specific instructions or other free text related to the administration of the medication (e.g., use left-arm IV only)"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-28",
"label" : "CP.6.1#28",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage information regarding a second provider witness to co-document administration."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-29",
"label" : "CP.6.1#29",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture the documentation of medication administration using a barcode scanner or imaging scanner (e.g., scanner capable of reading two dimensional symbologies)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-30",
"label" : "CP.6.1#30",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render an alert to the administering provider when an electronic identification device (e.g., barcode & scanner or RFID) is used to document the administration of the medication and one of the following is in error: right patient, right medication, right dose, right time, or right route or there has not been positive identification of the administering provider."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-31",
"label" : "CP.6.1#31",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage medication administration schedules on the record of medication administration - to allow user to adjust future authorized schedule as needed (e.g., delay, refused, unavailable)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-32",
"label" : "CP.6.1#32",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a notification to associated systems (e.g., pharmacy, ordering, food and nutrition services) of changes in schedules on the record of medication administration."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-33",
"label" : "CP.6.1#33",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture an acknowledgement from a user that a medication order has been reviewed including capturing the date, time and user credentials."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-34",
"label" : "CP.6.1#34",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture documentation of medication administration prior to pharmacy review."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-35",
"label" : "CP.6.1#35",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture, maintain and render as part of the medication administration record for infusions the actual date and times of the infusion including the start and stop times and any modifications to the infusion and the assessment status of the infusion."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-36",
"label" : "CP.6.1#36",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture, maintain, and render the patient's consent to have restricted medications administered, (e.g., Risk Evaluation and Mitigation Strategy (REMS))."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CP.6.1-37",
"label" : "CP.6.1#37",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY auto-populate the medication administration record as a by-product of verification of administering provider, patient, medication, dose, route and time according to scope of practice, organizational policy, and/or jurisdictional law.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.3.2#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-38",
"label" : "CP.6.1#38",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture, maintain, and present physiological parameters or task completion that must be checked and recorded prior to medication administration."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.6.1-39",
"label" : "CP.6.1#39",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain documentation that the right patient, right medication, right dose, right time, and right route were verified (e.g., using positive ID technology such as bar code scanning) at the time of administration."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CP.6.1-40",
"label" : "CP.6.1#40",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render a medication unique identifier (e.g., NDC, Structured Products Label (SPL) in the U.S. Realm or other standard product identifiers) according to jurisdictional law."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.